Systems and methods for improving HTTPS security

ABSTRACT

Systems and methods for HyperText Transfer Protocol (HTTP) HTTP Strict Transport Security (HSTS), are implemented by one or more servers associated with a gateway in a cloud based proxy. A method includes managing a preloaded list of HTTP Security (HTTPS) support of a plurality of domains; receiving a domain request from an HSTS application executed on a user device, wherein the HSTS application is configured to detect the domain request from a browser or application executed on the user device; and transmitting a response to the user device with header information related to support of HTTPS the domain.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to computer networking systemsand methods. More particularly, the present disclosure relates tosystems and methods for improving Hypertext Transfer Protocol (HTTP)Secure (HTTPS).

BACKGROUND OF THE DISCLOSURE

Eavesdroppers have always been successful in stealing private andconfidential information until extensive usage of HTTPS. Using HTTPSsolved the problem by encrypting data before sending it over a network.Due to human habit, a user typically types the domain name in browseraddress bar for an initial request (e.g., http://domain). Then browsermakes the initial request to http://domain. If the domain supportsHTTPS, it redirects to https://domain. After this redirection, data isencrypted before sending over the network. Before this redirection, theconnection is not encrypted, and the browser sends all HTTP header dataas plain text.

Disadvantageously, an eavesdropper can steal data from the initialrequest before redirection to HTTPS. The kind of data present in thefirst HTTP initial request can include Cookies, User-Agent and ServerAuthentication Credentials, and the like. Cookies are extensively usedto authenticate a user, store ads data, identification of the device andmany more purposes. User-Agent information includes browser details,browser version, and Operating System (OS) information. User-Agentinformation can be used to devise an attack to the user machine withknown and exposed issues with browser and OS and also zero-day attacks.

Many servers use the HTTP WWW-Authenticate mechanism to perform userauthentication. Once the browser authenticates with the server, itcaches the authentication and uses it for a subsequent request. Thefirst initial request before the redirecting to HTTPS will include thisinformation as well. Authorization header information can be exploitedto attack server and user both. Many browsers have started preloadingthe list of domains that support HTTPS. As soon as a user types thedomain in a browser address bar, the domain is replaced withhttps://domain, which makes the initial connection encrypted. This isreferred to as HTTP Strict Transport Security (HSTS).

There are various problems with this approach. First, not all browsersor applications support HSTS. Second, the browser or application needsto store preloaded list on the user device, resulting in unnecessarymemory utilization. Third, the browser or application does not have alldomains in the preloaded list, e.g., domains are constantly being addedto the Internet. Fourth, continuous browser or application updates areneeded to push the preloaded list to billions or more user devices whichare too intrusive. Fifth, by nature, the preloaded list is created byhumans and prone to human error. Specifically, once an erroneous domainlist is a push to the browser or application, it becomes a tedious,marathon task to fix.

A new more robust, less intrusive, manageable, and real-time solution isneeded.

BRIEF SUMMARY OF THE DISCLOSURE

In an exemplary embodiment, a method for HyperText Transfer Protocol(HTTP) HTTP Strict Transport (HSTS), implemented by one or more serversassociated with a gateway in a cloud based proxy, includes managing apreloaded list of HTTP Security (HTTPS) support of a plurality ofdomains; receiving a domain request from an HSTS application executed ona user device, wherein the HSTS application is configured to detect thedomain request from a browser or application executed on the userdevice; and transmitting a response to the user device with headerinformation related to support of HTTPS the domain. The method canfurther include, subsequent to the receiving and prior to thetransmitting, determining the support of HTTPS of the domain. Thedetermining can include sending a request to the domain withoutsensitive information from the domain request; and receiving a redirectfrom the domain. The determining can include checking the preloaded listand wherein the header information can include any exceptions based onthe preloaded list. The HSTS application removes sensitive informationfrom the domain request prior to the receiving. Communications betweenthe user device and the gateway are secure. The domain may not supportHSTS, and the method can further include transmitting the domain requestwith sensitive information in plain text between the gateway and thedomain.

In another exemplary embodiment, a gateway in a cloud based proxy,configured to implement HyperText Transfer Protocol (HTTP) HTTP StrictTransport (HSTS), includes a network interface, a data store, and aprocessor communicatively coupled to one another; and memory storingcomputer executable instructions, and in response to execution by theprocessor, the computer-executable instructions cause the processor toperform steps of managing a preloaded list of HTTP Security (HTTPS)support of a plurality of domains; receiving a domain request from anHSTS application executed on a user device, wherein the HSTS applicationis configured to detect the domain request from a browser or applicationexecuted on the user device; and transmitting a response to the userdevice with header information related to support of HTTPS the domain.The memory storing computer executable instructions, and in response toexecution by the processor, the computer-executable instructions canfurther cause the processor to perform steps of, subsequent to thereceiving and prior to the transmitting, determining the support ofHTTPS of the domain. The determining can include sending a request tothe domain without sensitive information from the domain request; andreceiving a redirect from the domain. The determining can includechecking the preloaded list and wherein the header information caninclude any exceptions based on the preloaded list. The HSTS applicationremoves sensitive information from the domain request prior to thereceiving. Communications between the user device and the gateway aresecure. The domain may not support HSTS, and wherein the memory storingcomputer executable instructions, and in response to execution by theprocessor, the computer-executable instructions can further cause theprocessor to perform steps of transmitting the domain request withsensitive information in plain text between the gateway and the domain.

In a further exemplary embodiment, a method for HyperText TransferProtocol (HTTP) HTTP Strict Transport (HSTS), implemented by a userdevice in communication with a gateway in a cloud based proxy, includesdetecting a domain request from a browser or application executed on theuser device by an HSTS application on the user device; securelyforwarding the domain request to a gateway; receiving a response fromthe gateway with header information related to HTTP Security (HTTPS)support of the domain; and, responsive to the domain supporting HTTPSbased on the header information, securely communicating with the domain.The browser or application may not support HSTS. The HSTS applicationremoves sensitive information from the domain request prior to theforwarding. The gateway determines whether the domain supports HTTPSindependent of the user device. The gateway can determine HTTPS supportthrough a request sent to the domain without sensitive information fromthe domain request; and reception of a redirect from the domain. Thegateway can determine HTTPS support by checking a preloaded list managedthereon of HTTPS supporting domains and wherein the header informationcan include any exceptions based on the preloaded list.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated and described herein withreference to the various drawings, in which like reference numbers areused to denote like system components/method steps, as appropriate, andin which:

FIG. 1 is a network diagram of a distributed security system;

FIG. 2 is a network diagram of the distributed security system of FIG. 1illustrating various components in more detail;

FIG. 3 is a block diagram of a server which may be used in thedistributed security system of FIG. 1 or with any other cloud-basedsystem;

FIG. 4 is a block diagram of a mobile device which may be used in thesystem of FIG. 1 or with any other cloud-based system;

FIG. 5 is a network diagram of a generalized cloud-based system;

FIG. 6 is a network diagram of a network with a distributed securitycloud providing DNS augmented security;

FIG. 7 is a network diagram of interactions between a user device, abrowser/app on the user device, and a server associated with a requesteddomain illustrating cookie hijacking;

FIG. 8 is a network diagram of interactions between a user device, abrowser/app on the user device, and a server associated with a requesteddomain illustrating User-Agent exposure;

FIG. 9 is a network diagram of interactions between a user device, abrowser/app on the user device, and a server associated with a requesteddomain illustrating Authorization exposure;

FIG. 10 is a network diagram of interactions between a user device, abrowser/app on the user device, a server associated with a requesteddomain, an HSTS application, and a cloud based proxy gatewayillustrating cookie security;

FIG. 11 is a network diagram of interactions between a user device, abrowser/app on the user device, a server associated with a requesteddomain, an HSTS application, and a cloud based proxy gatewayillustrating User-Agent security;

FIG. 12 is a network diagram of interactions between a user device, abrowser/app on the user device, a server associated with a requesteddomain, an HSTS application, and a cloud based proxy gatewayillustrating Authorization data security;

FIG. 13 is a network diagram of interactions between a user device, abrowser/app on the user device, a server associated with a requesteddomain, an HSTS application, and a cloud based proxy gatewayillustrating optimized cloud based HSTS; and

FIG. 14 is a network diagram of interactions between a user device, abrowser/app on the user device, a server associated with a requesteddomain, an HSTS application, and a cloud based proxy gatewayillustrating cloud based HSTS for non-HSTS domains.

DETAILED DESCRIPTION OF THE DISCLOSURE

Again, in various exemplary embodiments, the present disclosure relatesto systems and methods for improving Hypertext Transfer Protocol (HTTP)Secure (HTTPS). Specifically, the systems and methods solve thedeficiencies described herein related to HSTS using a cloud based proxy.In an exemplary embodiment, a cloud based security system is used as thecloud based proxy. A user device can be configured to forward trafficthrough the cloud based proxy. For example, the user device can includeclient software executed thereon, to forward traffic such as HTTPtraffic to the cloud based proxy. Internet access is controlled by theuser device which makes a CONNECT request for a domain, and the CONNECTrequest is through the cloud based proxy. The cloud based proxy replieswith a custom header informing the user device whether the domainsupports HTTPS. If the domain supports HTTPS, the user device removes acookie header, a user-agent header, and/or an authorization header fromthe first request. The domain server then will redirect to HTTPS and theconnection will be fully secure. All information will remain hidden fromany eavesdroppers. If the domain does not support HTTPS, it can open asecure and encrypted connection to the cloud based proxy, e.g., to agateway, to forward that domain request to provide partial protection(between the user device and the cloud based proxy). The cloud basedproxy can protect user confidentiality information against anyeavesdropper.

The cloud based proxy-based HSTS not only supports HSTS with enhancedsecurity, but also overcomes the aforementioned deficiencies of thetraditional browser-based approach. Advantageously, the preloaded listis not required on the user device; the cloud based proxy maintains suchlists in a unified manner. Accordingly, any new or updated domainsupporting HTTPS can be updated instantly, in real-time, in the cloudbased proxy alleviating any client updates. Thus, any human error can becorrected without introducing any delay. Further, the cloud based proxycan automatically detect any domains supporting HTTPS to avoid any humanpopulation of the preloaded list. Also, HSTS support is provided for allbrowsers and applications regardless of version, vendor, and actual HSTSsupport thereon. Further, non-HSTS domains can also be secured viaencrypted communication between the user device and the cloud basedproxy. The systems and methods improve latency associated with fullyencrypted tunnel protocols such as Internet Protocol Security (IPSec),avoids double encryption for HSTS supporting domains which is currentlypresent in protocols such as IPSec, improves battery performance of theuser device by reducing encryption processing thereon.

§ 1.0 Example High-Level System Architecture—Cloud-based Security System

Referring to FIG. 1, in an exemplary embodiment, a block diagramillustrates a distributed security system 100. The system 100 may, forexample, be implemented as an overlay network in a wide area network(WAN), such as the Internet, a local area network (LAN), or the like.The system 100 includes processing nodes (PN) 110, that proactivelydetect and preclude the distribution of security threats, e.g., malware,spyware, viruses, email spam, Data Leakage Prevention (DLP), contentfiltering, etc., and other undesirable content sent from or requested byan external system. The processing nodes 110 can also log activity andenforce policies, including logging changes to the various componentsand settings in the system 100. Example external systems may include anenterprise or external system 200, a computer device 220, and a mobiledevice 230, or other network and computing systems communicativelycoupled to the system 100. In an exemplary embodiment, each of theprocessing nodes 110 may include a decision system, e.g., datainspection engines that operate on a content item, e.g., a web page, afile, an email message, or some other data or data communication that issent from or requested by one of the external systems. In an exemplaryembodiment, all data destined for or received from the Internet isprocessed through one of the processing nodes 110. In another exemplaryembodiment, specific data specified by each external system, e.g., onlyemail, only executable files, etc., is process through one of theprocessing node 110.

Each of the processing nodes 110 may generate a decision vector D=[d1,d2, . . . , dn] for a content item of one or more parts C=[c1, c2, . . ., cm]. Each decision vector may identify a threat classification, e.g.,clean, spyware, malware, undesirable content, innocuous, spam email,unknown, etc. For example, the output of each element of the decisionvector D may be based on the output of one or more data inspectionengines. In an exemplary embodiment, the threat classification may bereduced to a subset of categories, e.g., violating, non-violating,neutral, unknown. Based on the subset classification, the processingnode 110 may allow distribution of the content item, precludedistribution of the content item, allow distribution of the content itemafter a cleaning process, or perform threat detection on the contentitem. In an exemplary embodiment, the actions taken by one of theprocessing nodes 110 may be determinative on the threat classificationof the content item and on a security policy of the external system towhich the content item is being sent from or from which the content itemis being requested by. A content item is violating if, for any partC=[c1, c2, . . . , cm] of the content item, at any of the processingnodes 110, any one of the data inspection engines generates an outputthat results in a classification of “violating.”

Each of the processing nodes 110 may be implemented by one or more ofcomputer and communications devices, e.g., server computers, gateways,switches, etc., such as the server 300 described in FIG. 3. In anexemplary embodiment, the processing nodes 110 may serve as an accesslayer 150. The access layer 150 may, for example, provide externalsystem access to the security system 100. In an exemplary embodiment,each of the processing nodes 110 may include Internet gateways and oneor more servers, and the processing nodes 110 may be distributed througha geographic region, e.g., throughout a country, region, campus, etc.According to a service agreement between a provider of the system 100and an owner of an external system, the system 100 may thus providesecurity protection to the external system at any location throughoutthe geographic region.

Data communications may be monitored by the system 100 in a variety ofways, depending on the size and data requirements of the externalsystem. For example, an enterprise 200 may have multiple routers,switches, etc. that are used to communicate over the Internet, and therouters, switches, etc. may be configured to establish communicationsthrough the nearest (in traffic communication time, for example)processing node 110. A mobile device 230 may be configured tocommunicated to a nearest processing node 110 through any availablewireless access device, such as an access point, or a cellular gateway.A single computer device 220, such as a consumer's personal computer,may have its browser and email program configured to access the nearestprocessing node 110, which, in turn, serves as a proxy for the computerdevice 220. Alternatively, an Internet provider may have all of itscustomer traffic processed through the processing nodes 110.

In an exemplary embodiment, the processing nodes 110 may communicatewith one or more authority nodes (AN) 120. The authority nodes 120 maystore policy data for each external system and may distribute the policydata to each of the processing nodes 110. The policy may, for example,define security policies for a protected system, e.g., security policiesfor the enterprise 200. Example policy data may define access privilegesfor users, websites and/or content that is disallowed, restricteddomains, etc. The authority nodes 120 may distribute the policy data tothe processing nodes 110. In an exemplary embodiment, the authoritynodes 120 may also distribute threat data that includes theclassifications of content items according to threat classifications,e.g., a list of known viruses, a list of known malware sites, spam emaildomains, a list of known phishing sites, etc. The distribution of threatdata between the processing nodes 110 and the authority nodes 120 may beimplemented by push and pull distribution schemes described in moredetail below. In an exemplary embodiment, each of the authority nodes120 may be implemented by one or more computer and communicationdevices, e.g., server computers, gateways, switches, etc., such as theserver 300 described in FIG. 3. In some exemplary embodiments, theauthority nodes 120 may serve as an application layer 170. Theapplication layer 170 may, for example, manage and provide policy data,threat data, and data inspection engines and dictionaries for theprocessing nodes 110.

Other application layer functions may also be provided in theapplication layer 170, such as a user interface (UI) front-end 130. Theuser interface front-end 130 may provide a user interface through whichusers of the external systems may provide and define security policies,e.g., whether email traffic is to be monitored, whether certain websitesare to be precluded, etc. Another application capability that may beprovided through the user interface front-end 130 is security analysisand log reporting. The underlying data on which the security analysisand log reporting functions operate are stored in logging nodes (LN)140, which serve as a data logging layer 160. Each of the logging nodes140 may store data related to security operations and network trafficprocessed by the processing nodes 110 for each external system. In anexemplary embodiment, the logging node 140 data may be anonymized sothat data identifying an enterprise is removed or obfuscated. Forexample, identifying data may be removed to provide an overall systemsummary of security processing for all enterprises and users withoutrevealing the identity of any one account. Alternatively, identifyingdata may be obfuscated, e.g., provide a random account number each timeit is accessed, so that an overall system summary of security processingfor all enterprises and users may be broken out by accounts withoutrevealing the identity of any one account. In another exemplaryembodiment, the identifying data and/or logging node 140 data may befurther encrypted, e.g., so that only the enterprise (or user if asingle user account) may have access to the logging node 140 data forits account. Other processes of anonymizing, obfuscating, or securinglogging node 140 data may also be used. Note, as described herein, thesystems and methods for tracking and auditing changes in a multi-tenantcloud system can be implemented in the data logging layer 160, forexample.

In an exemplary embodiment, an access agent 180 may be included in theexternal systems. For example, the access agent 180 is deployed in theenterprise 200. The access agent 180 may, for example, facilitatesecurity processing by providing a hash index of files on a clientdevice to one of the processing nodes 110, or may facilitateauthentication functions with one of the processing nodes 110, e.g., byassigning tokens for passwords and sending only the tokens to aprocessing node so that transmission of passwords beyond the networkedge of the enterprise is minimized. Other functions and processes mayalso be facilitated by the access agent 180. In an exemplary embodiment,the processing node 110 may act as a forward proxy that receives userrequests to external servers addressed directly to the processing node110. In another exemplary embodiment, the processing node 110 may accessuser requests that are passed through the processing node 110 in atransparent mode. A protected system, e.g., enterprise 200, may, forexample, choose one or both of these modes. For example, a browser maybe configured either manually or through the access agent 180 to accessthe processing node 110 in a forward proxy mode. In the forward proxymode, all accesses are addressed to the processing node 110.

In an exemplary embodiment, an enterprise gateway may be configured sothat user requests are routed through the processing node 110 byestablishing a communication tunnel between enterprise gateway and theprocessing node 110. For establishing the tunnel, existing protocolssuch as generic routing encapsulation (GRE), layer two tunnelingprotocol (L2TP), or other Internet Protocol (IP) security protocols maybe used. In another exemplary embodiment, the processing nodes 110 maybe deployed at Internet service provider (ISP) nodes. The ISP nodes mayredirect subject traffic to the processing nodes 110 in a transparentproxy mode. Protected systems, such as the enterprise 200, may use amultiprotocol label switching (MPLS) class of service for indicating thesubject traffic that is to be redirected. For example, at the within theenterprise, the access agent 180 may be configured to perform MPLSlabeling. In another transparent proxy mode exemplary embodiment, aprotected system, such as the enterprise 200, may identify theprocessing node 110 as a next hop router for communication with theexternal servers.

Generally, the distributed security system 100 may generally refer to anexemplary cloud-based security system. Other cloud-based securitysystems and generalized cloud-based systems are contemplated for thesystems and methods for tracking and auditing changes in a multi-tenantcloud system. Cloud computing systems and methods abstract away physicalservers, storage, networking, etc. and instead offer these as on-demandand elastic resources. The National Institute of Standards andTechnology (NIST) provides a concise and specific definition whichstates cloud computing is a model for enabling convenient, on-demandnetwork access to a shared pool of configurable computing resources(e.g., networks, servers, storage, applications, and services) that canbe rapidly provisioned and released with minimal management effort orservice provider interaction. Cloud computing differs from the classicclient-server model by providing applications from a server that areexecuted and managed by a client's web browser, with no installed clientversion of an application required. Centralization gives cloud serviceproviders complete control over the versions of the browser-basedapplications provided to clients, which removes the need for versionupgrades or license management on individual client computing devices.The phrase “software as a service” (SaaS) is sometimes used to describeapplication programs offered through cloud computing. A common shorthandfor a provided cloud computing service (or even an aggregation of allexisting cloud services) is “the cloud.” The distributed security system100 is illustrated herein as one exemplary embodiment of a cloud-basedsystem, and those of ordinary skill in the art will recognize thetracking and auditing systems and methods contemplate operation on anycloud-based system.

§ 2.0 Example Detailed System Architecture and Operation

Referring to FIG. 2, in an exemplary embodiment, a block diagramillustrates various components of the distributed security system 100 inmore detail. Although FIG. 2 illustrates only one representativecomponent processing node 110, authority node 120 and logging node 140,those of ordinary skill in the art will appreciate there may be many ofeach of the component nodes 110, 120 and 140 present in the system 100.A wide area network (WAN) 101, such as the Internet, or some othercombination of wired and/or wireless networks, communicatively couplesthe processing node 110, the authority node 120, and the logging node140 to one another. The external systems 200, 220 and 230 likewisecommunicate over the WAN 101 with each other or other data providers andpublishers. Some or all of the data communication of each of theexternal systems 200, 220 and 230 may be processed through theprocessing node 110.

FIG. 2 also shows the enterprise 200 in more detail. The enterprise 200may, for example, include a firewall (FW) 202 protecting an internalnetwork that may include one or more enterprise servers 216, alightweight directory access protocol (LDAP) server 212, and other dataor data stores 214. Another firewall 203 may protect an enterprisesubnet that can include user computers 206 and 208 (e.g., laptop anddesktop computers). The enterprise 200 may communicate with the WAN 101through one or more network devices, such as a router, gateway, switch,etc. The LDAP server 212 may store, for example, user login credentialsfor registered users of the enterprise 200 system. Such credentials mayinclude user identifiers, login passwords, and a login historyassociated with each user identifier. The other data stores 214 mayinclude sensitive information, such as bank records, medical records,trade secret information, or any other information warranting protectionby one or more security measures.

In an exemplary embodiment, a client access agent 180A may be includedon a client computer 206. The client access agent 180A may, for example,facilitate security processing by providing a hash index of files on theuser computer 206 to a processing node 110 for malware, virus detection,etc. Other security operations may also be facilitated by the accessagent 180A. In another exemplary embodiment, a server access agent 180may facilitate authentication functions with the processing node 110,e.g., by assigning tokens for passwords and sending only the tokens tothe processing node 110 so that transmission of passwords beyond thenetwork edge of the enterprise 200 is minimized. Other functions andprocesses may also be facilitated by the server access agent 180 b. Thecomputer device 220 and the mobile device 230 may also store informationwarranting security measures, such as personal bank records, medicalinformation, and login information, e.g., login information to thecomputers 206 of the enterprise 200, or to some other secured dataprovider server. The computer device 220 and the mobile device 230 canalso store information warranting security measures, such as personalbank records, medical information, and login information, e.g., logininformation to a server 216 of the enterprise 200, or to some othersecure data provider server.

§ 2.1 Example Processing Node Architecture

In an exemplary embodiment, the processing nodes 110 are external tonetwork edges of the external systems 200, 220 and 230. Each of theprocessing nodes 110 stores security policy data 113 received from theauthority node 120 and monitors content items requested by or sent fromthe external systems 200, 220 and 230. In an exemplary embodiment, eachof the processing nodes 110 may also store a detection process filter112 and/or threat data 114 to facilitate the decision of whether acontent item should be processed for threat detection. A processing nodemanager 118 may manage each content item in accordance with the securitypolicy data 113, and the detection process filter 112 and/or threat data114, if stored at the processing node 110, so that security policies fora plurality of external systems in data communication with theprocessing node 110 are implemented external to the network edges foreach of the external systems 200, 220 and 230. For example, depending onthe classification resulting from the monitoring, the content item maybe allowed, precluded, or threat detected. In general, content itemsthat are already classified as “clean” or not posing a threat can beallowed, while those classified as “violating” may be precluded. Thosecontent items having an unknown status, e.g., content items that havenot been processed by the system 100, may be threat detected to classifythe content item according to threat classifications.

The processing node 110 may include a state manager 116A. The statemanager 116A may be used to maintain the authentication and theauthorization states of users that submit requests to the processingnode 110. Maintenance of the states through the state manager 116A mayminimize the number of authentication and authorization transactionsthat are necessary to process a request. The processing node 110 mayalso include an epoch processor 116B. The epoch processor 116B may beused to analyze authentication data that originated at the authoritynode 120. The epoch processor 116B may use an epoch ID to validatefurther the authenticity of authentication data. The processing node 110may further include a source processor 116C. The source processor 116Cmay be used to verify the source of authorization and authenticationdata. The source processor 116C may identify improperly obtainedauthorization and authentication data, enhancing the security of thenetwork. Collectively, the state manager 116A, the epoch processor 116B,and the source processor 116C operate as data inspection engines.

Because the amount of data being processed by the processing nodes 110may be substantial, the detection processing filter 112 may be used asthe first stage of an information lookup procedure. For example, thedetection processing filter 112 may be used as a front end to a lookingof the threat data 114. Content items may be mapped to index values ofthe detection processing filter 112 by a hash function that operates onan information key derived from the information item. The informationkey is hashed to generate an index value (i.e., a bit position). A valueof zero in a bit position in the guard table can indicate, for example,absence of information, while a one in that bit position can indicatepresence of information. Alternatively, a one could be used to representabsence, and a zero to represent presence. Each content item may have aninformation key that is hashed. For example, the processing node manager118 may identify the Uniform Resource Locator (URL) address of URLrequests as the information key and hash the URL address; or mayidentify the file name and the file size of an executable fileinformation key and hash the file name and file size of the executablefile. Hashing an information key to generate an index and checking a bitvalue at the index in the detection processing filter 112 generallyrequires less processing time than actually searching threat data 114.The use of the detection processing filter 112 may improve the failurequery (i.e., responding to a request for absent information) performanceof database queries and/or any general information queries. Because datastructures are generally optimized to access information that is presentin the structures, failure query performance has a greater effect on thetime required to process information searches for very rarely occurringitems, e.g., the presence of file information in a virus scan log or acache where many or most of the files transferred in a network have notbeen scanned or cached. Using the detection processing filter 112,however, the worst case additional cost is only on the order of one, andthus its use for most failure queries saves on the order of m log m,where m is the number of information records present in the threat data114.

The detection processing filter 112 thus improves performance of querieswhere the answer to a request for information is usually positive. Suchinstances may include, for example, whether a given file has been virusscanned, whether content at a given URL has been scanned forinappropriate (e.g., pornographic) content, whether a given fingerprintmatches any of a set of stored documents, and whether a checksumcorresponds to any of a set of stored documents. Thus, if the detectionprocessing filter 112 indicates that the content item has not beenprocessed, then a worst case null lookup operation into the threat data114 is avoided, and a threat detection can be implemented immediately.The detection processing filter 112 thus complements the threat data 114that capture positive information. In an exemplary embodiment, thedetection processing filter 112 may be a Bloom filter implemented by asingle hash function. The Bloom filter may be sparse table, i.e., thetables include many zeros and few ones, and the hash function is chosento minimize or eliminate false negatives which are, for example,instances where an information key is hashed to a bit position and thatbit position indicates that the requested information is absent when itis actually present.

§ 2.2 Example Authority Node Architecture

In general, the authority node 120 includes a data store that storesmaster security policy data 123 for each of the external systems 200,220 and 230. An authority node manager 128 may be used to manage themaster security policy data 123, e.g., receive input from users of eachof the external systems defining different security policies, and maydistribute the master security policy data 123 to each of the processingnodes 110. The processing nodes 110 then store a local copy of thesecurity policy data 113. The authority node 120 may also store a masterdetection process filter 122. The detection processing filter 122 mayinclude data indicating whether content items have been processed by oneor more of the data inspection engines 116 in any of the processingnodes 110. The authority node manager 128 may be used to manage themaster detection processing filter 122, e.g., receive updates from aprocessing nodes 110 when the processing node 110 has processed acontent item and update the master detection processing filter 122. Forexample, the master detection processing filter 122 may be distributedto the processing nodes 110, which then store a local copy of thedetection processing filter 112.

In an exemplary embodiment, the authority node 120 may include an epochmanager 126. The epoch manager 126 may be used to generateauthentication data associated with an epoch ID. The epoch ID of theauthentication data is a verifiable attribute of the authentication datathat can be used to identify fraudulently created authentication data.In an exemplary embodiment, the detection processing filter 122 may be aguard table. The processing node 110 may, for example, use theinformation in the local detection processing filter 112 to quicklydetermine the presence and/or absence of information, e.g., whether aparticular URL has been checked for malware; whether a particularexecutable has been virus scanned, etc. The authority node 120 may alsostore master threat data 124. The master threat data 124 may classifycontent items by threat classifications, e.g., a list of known viruses,a list of known malware sites, spam email domains, list of known ordetected phishing sites, etc. The authority node manager 128 may be usedto manage the master threat data 124, e.g., receive updates from theprocessing nodes 110 when one of the processing nodes 110 has processeda content item and update the master threat data 124 with any pertinentresults. In some implementations, the master threat data 124 may bedistributed to the processing nodes 110, which then store a local copyof the threat data 114. In another exemplary embodiment, the authoritynode 120 may also monitor the health of each of the processing nodes110, e.g., the resource availability in each of the processing nodes110, detection of link failures, etc. Based on the observed health ofeach of the processing nodes 110, the authority node 120 may redirecttraffic among the processing nodes 110 and/or balance traffic among theprocessing nodes 110. Other remedial actions and processes may also befacilitated by the authority node 120.

§ 2.3 Example Processing Node and Authority Node Communications

The processing node 110 and the authority node 120 may be configuredaccording to one or more push and pull processes to manage content itemsaccording to security policy data 113 and/or 123, detection processfilters 112 and/or 122, and the threat data 114 and/or 124. In a threatdata push implementation, each of the processing nodes 110 stores policydata 113 and threat data 114. The processing node manager 118 determineswhether a content item requested by or transmitted from an externalsystem is classified by the threat data 114. If the content item isdetermined to be classified by the threat data 114, then the processingnode manager 118 may manage the content item according to the securityclassification of the content item and the security policy of theexternal system. If, however, the content item is determined to not beclassified by the threat data 114, then the processing node manager 118may cause one or more of the data inspection engines 117 to perform thethreat detection processes to classify the content item according to athreat classification. Once the content item is classified, theprocessing node manager 118 generates a threat data update that includesdata indicating the threat classification for the content item from thethreat detection process, and transmits the threat data update to anauthority node 120.

The authority node manager 128, in response to receiving the threat dataupdate, updates the master threat data 124 stored in the authority nodedata store according to the threat data update received from theprocessing node 110. In an exemplary embodiment, the authority nodemanager 128 may automatically transmit the updated threat data to theother processing nodes 110. Accordingly, threat data for new threats asthe new threats are encountered are automatically distributed to eachprocessing node 110. Upon receiving the new threat data from theauthority node 120, each of processing node managers 118 may store theupdated threat data in the locally stored threat data 114.

In a threat data pull and push implementation, each of the processingnodes 110 stores policy data 113 and threat data 114. The processingnode manager 118 determines whether a content item requested by ortransmitted from an external system is classified by the threat data114. If the content item is determined to be classified by the threatdata 114, then the processing node manager 118 may manage the contentitem according to the security classification of the content item andthe security policy of the external system. If, however, the contentitem is determined to not be classified by the threat data, then theprocessing node manager 118 may request responsive threat data for thecontent item from the authority node 120. Because processing a contentitem may consume valuable resource and time, in some implementations theprocessing node 110 may first check with the authority node 120 forthreat data 114 before committing such processing resources.

The authority node manager 128 may receive the responsive threat datarequest from the processing node 110 and may determine if the responsivethreat data is stored in the authority node data store. If responsivethreat data is stored in the master threat data 124, then the authoritynode manager 128 provide a reply that includes the responsive threatdata to the processing node 110 so that the processing node manager 118may manage the content item in accordance with the security policy data113 and the classification of the content item. Conversely, if theauthority node manager 128 determines that responsive threat data is notstored in the master threat data 124, then the authority node manager128 may provide a reply that does not include the responsive threat datato the processing node 110. In response, the processing node manager 118can cause one or more of the data inspection engines 116 to perform thethreat detection processes to classify the content item according to athreat classification. Once the content item is classified, theprocessing node manager 118 generates a threat data update that includesdata indicating the threat classification for the content item from thethreat detection process, and transmits the threat data update to anauthority node 120. The authority node manager 128 can then update themaster threat data 124. Thereafter, any future requests related toresponsive threat data for the content item from other processing nodes110 can be readily served with responsive threat data.

In a detection process filter and threat data push implementation, eachof the processing nodes 110 stores a detection process filter 112,policy data 113, and threat data 114. The processing node manager 118accesses the detection process filter 112 to determine whether thecontent item has been processed. If the processing node manager 118determines that the content item has been processed, it may determine ifthe content item is classified by the threat data 114. Because thedetection process filter 112 has the potential for a false positive, alookup in the threat data 114 may be implemented to ensure that a falsepositive has not occurred. The initial check of the detection processfilter 112, however, may eliminate many null queries to the threat data114, which, in turn, conserves system resources and increasesefficiency. If the content item is classified by the threat data 114,then the processing node manager 118 may manage the content item inaccordance with the security policy data 113 and the classification ofthe content item. Conversely, if the processing node manager 118determines that the content item is not classified by the threat data114, or if the processing node manager 118 initially determines throughthe detection process filter 112 that the content item is not classifiedby the threat data 114, then the processing node manager 118 may causeone or more of the data inspection engines 116 to perform the threatdetection processes to classify the content item according to a threatclassification. Once the content item is classified, the processing nodemanager 118 generates a threat data update that includes data indicatingthe threat classification for the content item from the threat detectionprocess, and transmits the threat data update to one of the authoritynodes 120.

The authority node manager 128, in turn, may update the master threatdata 124 and the master detection process filter 122 stored in theauthority node data store according to the threat data update receivedfrom the processing node 110. In an exemplary embodiment, the authoritynode manager 128 may automatically transmit the updated threat data anddetection processing filter to other processing nodes 110. Accordingly,threat data and the detection processing filter for new threats as thenew threats are encountered are automatically distributed to eachprocessing node 110, and each processing node 110 may update its localcopy of the detection processing filter 112 and threat data 114.

In a detection process filter and threat data pull and pushimplementation, each of the processing nodes 110 stores a detectionprocess filter 112, policy data 113, and threat data 114. The processingnode manager 118 accesses the detection process filter 112 to determinewhether the content item has been processed. If the processing nodemanager 118 determines that the content item has been processed, it maydetermine if the content item is classified by the threat data 114.Because the detection process filter 112 has the potential for a falsepositive, a lookup in the threat data 114 can be implemented to ensurethat a false positive has not occurred. The initial check of thedetection process filter 112, however, may eliminate many null queriesto the threat data 114, which, in turn, conserves system resources andincreases efficiency. If the processing node manager 118 determines thatthe content item has not been processed, it may request responsivethreat data for the content item from the authority node 120. Becauseprocessing a content item may consume valuable resource and time, insome implementations the processing node 110 may first check with theauthority node 120 for threat data 114 before committing such processingresources.

The authority node manager 128 may receive the responsive threat datarequest from the processing node 110 and may determine if the responsivethreat data is stored in the authority node data 120 store. Ifresponsive threat data is stored in the master threat data 124, then theauthority node manager 128 provides a reply that includes the responsivethreat data to the processing node 110 so that the processing nodemanager 118 can manage the content item in accordance with the securitypolicy data 112 and the classification of the content item, and furtherupdate the local detection processing filter 112. Conversely, if theauthority node manager 128 determines that responsive threat data is notstored in the master threat data 124, then the authority node manager128 may provide a reply that does not include the responsive threat datato the processing node 110. In response, the processing node manager 118may cause one or more of the data inspection engines 116 to perform thethreat detection processes to classify the content item according to athreat classification. Once the content item is classified, theprocessing node manager 118 generates a threat data update that includesdata indicating the threat classification for the content item from thethreat detection process, and transmits the threat data update to anauthority node 120. The authority node manager 128 may then update themaster threat data 124. Thereafter, any future requests for related toresponsive threat data for the content item from other processing nodes110 can be readily served with responsive threat data.

The various push and pull data exchange processes provided above areexemplary processes for which the threat data and/or detection processfilters may be updated in the system 100 of FIGS. 1 and 2. Other updateprocesses, however, are contemplated with the present invention. Thedata inspection engines 116, processing node manager 118, authority nodemanager 128, user interface manager 132, logging node manager 148, andauthority agent 180 may be realized by instructions that upon executioncause one or more processing devices to carry out the processes andfunctions described above. Such instructions can, for example, includeinterpreted instructions, such as script instructions, e.g., JavaScriptor ECMAScript instructions, or executable code, or other instructionsstored in a non-transitory computer readable medium. Other processingarchitectures can also be used, e.g., a combination of speciallydesigned hardware and software, for example.

§ 3.0 Exemplary Server Architecture

Referring to FIG. 3, in an exemplary embodiment, a block diagramillustrates a server 300 which may be used in the system 100, in othersystems, or standalone. Any of the processing nodes 110, the authoritynodes 120, and the logging nodes 140 may be formed through one or moreservers 300. Further, the computer device 220, the mobile device 230,the servers 208, 216, etc. may include the server 300 or a similarstructure. The server 300 may be a digital computer that, in terms ofhardware architecture, generally includes a processor 302, input/output(I/O) interfaces 304, a network interface 306, a data store 308, andmemory 310. It should be appreciated by those of ordinary skill in theart that FIG. 3 depicts the server 300 in an oversimplified manner, anda practical embodiment may include additional components and suitablyconfigured processing logic to support known or conventional operatingfeatures that are not described in detail herein. The components (302,304, 306, 308, and 310) are communicatively coupled via a localinterface 312. The local interface 312 may be, for example but notlimited to, one or more buses or other wired or wireless connections, asis known in the art. The local interface 312 may have additionalelements, which are omitted for simplicity, such as controllers, buffers(caches), drivers, repeaters, and receivers, among many others, toenable communications. Further, the local interface 312 may includeaddress, control, and/or data connections to enable appropriatecommunications among the aforementioned components.

The processor 302 is a hardware device for executing softwareinstructions. The processor 302 may be any custom made or commerciallyavailable processor, a central processing unit (CPU), an auxiliaryprocessor among several processors associated with the server 300, asemiconductor-based microprocessor (in the form of a microchip or chipset), or generally any device for executing software instructions. Whenthe server 300 is in operation, the processor 302 is configured toexecute software stored within the memory 310, to communicate data toand from the memory 310, and to generally control operations of theserver 300 pursuant to the software instructions. The I/O interfaces 304may be used to receive user input from and/or for providing systemoutput to one or more devices or components. User input may be providedvia, for example, a keyboard, touch pad, and/or a mouse. System outputmay be provided via a display device and a printer (not shown). I/Ointerfaces 304 may include, for example, a serial port, a parallel port,a small computer system interface (SCSI), a serial ATA (SATA), a fibrechannel, Infiniband, iSCSI, a PCI Express interface (PCI-x), an infrared(IR) interface, a radio frequency (RF) interface, and/or a universalserial bus (USB) interface.

The network interface 306 may be used to enable the server 300 tocommunicate over a network, such as the Internet, the WAN 101, theenterprise 200, and the like, etc. The network interface 306 mayinclude, for example, an Ethernet card or adapter (e.g., 10BaseT, FastEthernet, Gigabit Ethernet, 10 GbE) or a wireless local area network(WLAN) card or adapter (e.g., 802.11a/b/g/n). The network interface 306may include address, control, and/or data connections to enableappropriate communications on the network. A data store 308 may be usedto store data. The data store 308 may include any of volatile memoryelements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM,and the like)), nonvolatile memory elements (e.g., ROM, hard drive,tape, CDROM, and the like), and combinations thereof. Moreover, the datastore 308 may incorporate electronic, magnetic, optical, and/or othertypes of storage media. In one example, the data store 308 may belocated internal to the server 300 such as, for example, an internalhard drive connected to the local interface 312 in the server 300.Additionally, in another embodiment, the data store 308 may be locatedexternal to the server 300 such as, for example, an external hard driveconnected to the I/O interfaces 304 (e.g., SCSI or USB connection). In afurther embodiment, the data store 308 may be connected to the server300 through a network, such as, for example, a network attached fileserver.

The memory 310 may include any of volatile memory elements (e.g., randomaccess memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatilememory elements (e.g., ROM, hard drive, tape, CDROM, etc.), andcombinations thereof. Moreover, the memory 310 may incorporateelectronic, magnetic, optical, and/or other types of storage media. Notethat the memory 310 may have a distributed architecture, where variouscomponents are situated remotely from one another, but can be accessedby the processor 302. The software in memory 310 may include one or moresoftware programs, each of which includes an ordered listing ofexecutable instructions for implementing logical functions. The softwarein the memory 310 includes a suitable operating system (O/S) 314 and oneor more programs 316. The operating system 314 essentially controls theexecution of other computer programs, such as the one or more programs316, and provides scheduling, input-output control, file and datamanagement, memory management, and communication control and relatedservices. The one or more programs 316 may be configured to implementthe various processes, algorithms, methods, techniques, etc. describedherein.

§ 4.0 Exemplary Mobile Device Architecture

Referring to FIG. 4, in an exemplary embodiment, a block diagramillustrates a mobile device 400, which may be used in the system 100 orthe like. The mobile device 400 can be a digital device that, in termsof hardware architecture, generally includes a processor 402,input/output (I/O) interfaces 404, a radio 406, a data store 408, andmemory 410. It should be appreciated by those of ordinary skill in theart that FIG. 4 depicts the mobile device 400 in an oversimplifiedmanner, and a practical embodiment may include additional components andsuitably configured processing logic to support known or conventionaloperating features that are not described in detail herein. Thecomponents (402, 404, 406, 408, and 410) are communicatively coupled viaa local interface 412. The local interface 412 can be, for example butnot limited to, one or more buses or other wired or wirelessconnections, as is known in the art. The local interface 412 can haveadditional elements, which are omitted for simplicity, such ascontrollers, buffers (caches), drivers, repeaters, and receivers, amongmany others, to enable communications. Further, the local interface 412may include address, control, and/or data connections to enableappropriate communications among the aforementioned components.

The processor 402 is a hardware device for executing softwareinstructions. The processor 402 can be any custom made or commerciallyavailable processor, a central processing unit (CPU), an auxiliaryprocessor among several processors associated with the mobile device400, a semiconductor-based microprocessor (in the form of a microchip orchip set), or generally any device for executing software instructions.When the mobile device 400 is in operation, the processor 402 isconfigured to execute software stored within the memory 410, tocommunicate data to and from the memory 410, and to generally controloperations of the mobile device 400 pursuant to the softwareinstructions. In an exemplary embodiment, the processor 402 may includean optimized mobile processor such as optimized for power consumptionand mobile applications. The I/O interfaces 404 can be used to receiveuser input from and/or for providing system output. User input can beprovided via, for example, a keypad, a touch screen, a scroll ball, ascroll bar, buttons, barcode scanner, and the like. System output can beprovided via a display device such as a liquid crystal display (LCD),touch screen, and the like. The I/O interfaces 404 can also include, forexample, a serial port, a parallel port, a small computer systeminterface (SCSI), an infrared (IR) interface, a radio frequency (RF)interface, a universal serial bus (USB) interface, and the like. The I/Ointerfaces 404 can include a graphical user interface (GUI) that enablesa user to interact with the mobile device 400. Additionally, the I/Ointerfaces 404 may further include an imaging device, i.e. camera, videocamera, etc.

The radio 406 enables wireless communication to an external accessdevice or network. Any number of suitable wireless data communicationprotocols, techniques, or methodologies can be supported by the radio406, including, without limitation: RF; IrDA (infrared); BLUETOOTH® (andother wireless communications, such as those falling within the IEEE802.15.1 protocol); ZigBee (and other variants of the IEEE 802.15protocol); IEEE 802.11 (any variation); IEEE 802.16 (WiMAX or any othervariation); Direct Sequence Spread Spectrum; Frequency Hopping SpreadSpectrum; Long Term Evolution (LTE); cellular/wireless/cordlesstelecommunication protocols (e.g., 3G/4G, etc.); wireless home networkcommunication protocols; paging network protocols; magnetic induction;satellite data communication protocols; wireless hospital or health carefacility network protocols such as those operating in the WMTS bands;GPRS; proprietary wireless data communication protocols such as variantsof Wireless USB; and any other protocols for wireless communication. Thedata store 408 may be used to store data. The data store 408 may includeany of volatile memory elements (e.g., random access memory (RAM, suchas DRAM, SRAM, SDRAM, and the like)), nonvolatile memory elements (e.g.,ROM, hard drive, tape, CDROM, and the like), and combinations thereof.Moreover, the data store 408 may incorporate electronic, magnetic,optical, and/or other types of storage media.

The memory 410 may include any of volatile memory elements (e.g., randomaccess memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatilememory elements (e.g., ROM, hard drive, etc.), and combinations thereof.Moreover, the memory 410 may incorporate electronic, magnetic, optical,and/or other types of storage media. Note that the memory 410 may have adistributed architecture, where various components are situated remotelyfrom one another, but can be accessed by the processor 402. The softwarein memory 410 can include one or more software programs, each of whichincludes an ordered listing of executable instructions for implementinglogical functions. In the example of FIG. 4, the software in the memory410 includes a suitable operating system (O/S) 414 and programs 416. Theoperating system 414 essentially controls the execution of othercomputer programs and provides scheduling, input-output control, fileand data management, memory management, and communication control andrelated services. The programs 416 may include various applications,add-ons, etc. configured to provide end user functionality with themobile device 400. For example, exemplary programs 416 may include, butnot limited to, a web browser, social networking applications, streamingmedia applications, games, mapping and location applications, electronicmail applications, financial applications, and the like. In a typicalexample, the end user typically uses one or more of the programs 416along with a network such as the system 100.

§ 5.0 Exemplary General Cloud System

Referring to FIG. 5, in an exemplary embodiment, a cloud system 500 isillustrated for implementing the systems and methods described hereinfor tracking and auditing changes in a multi-tenant cloud system. Thecloud system 500 includes one or more cloud nodes (CN) 502communicatively coupled to the Internet 504. The cloud nodes 502 mayinclude the processing nodes 110, the server 300, or the like. That is,the cloud system 500 may include the distributed security system 100 oranother implementation of a cloud-based system, such as a systemproviding different functionality from security. In the cloud system500, traffic from various locations (and various devices locatedtherein) such as a regional office 510, headquarters 520, variousemployee's homes 530, mobile laptop 540, and mobile device 542communicates to the cloud through the cloud nodes 502. That is; each ofthe locations 510, 520, 530, 540, 542 is communicatively coupled to theInternet 504 through the cloud nodes 502. For security, the cloud system500 may be configured to perform various functions such as spamfiltering, uniform resource locator (URL) filtering, antivirusprotection, bandwidth control, data loss prevention, zero-dayvulnerability protection, web 2.0 features, and the like. In anexemplary embodiment, the cloud system 500 and the distributed securitysystem 100 may be viewed as Security-as-a-Service through the cloud. Ingeneral, the cloud system 500 can be configured to perform any functionin a multi-tenant environment. For example, the cloud system 500 canprovide content, a collaboration between users, storage, applicationhosting, and the like.

In an exemplary embodiment, the cloud system 500 can utilize the systemsand methods for tracking and auditing changes in a multi-tenant cloudsystem. That is, the cloud system 500 can track and audit administratoractivity associated with the cloud system 500 in a segregated andoverlaid fashion from the application functions performed by the cloudsystem 500. This segregated and overlaid fashion decouples the trackingand auditing from application logic, maximizing resources and minimizingdevelopment complexity and runtime processing. The cloud system 500 (andthe system 100) can be offloaded from complex tracking and auditingfunctions so that it can provide its primary function. In the context ofa distributed security system, the tracking and auditing systems andmethods enable accountability, intrusion detection, problem diagnosis,and data reconstruction, all in an optimized fashion considering theexponential growth in cloud-based systems.

§ 6.0 DNS Augmented Security

In an exemplary embodiment, the cloud system 500 and/or the distributedsecurity system 100 can be used to perform DNS surrogation.Specifically, DNS surrogation can be a framework for distributed orcloud-based security/monitoring as is described herein. Endpointsecurity is no longer effective as deployments move to the cloud withusers accessing content from a plurality of devices in an anytime,anywhere connected manner. As such, cloud-based security is the mosteffective means to ensure network protection where different devices areused to access network resources. Traffic inspection in the distributedsecurity system 100 and the cloud-based system 500 is performed in anin-line manner, i.e. the processing nodes 110 and the cloud nodes 502are in the data path of connecting users. Another approach can include apassive approach to the data path. DNS is one of the most fundamental IPprotocols. With DNS surrogation as a technique, it is proposed to useDNS for dynamic routing of traffic, per-user authentication and policyenforcement, and the like.

In conjunction with the cloud system 500 and/or the distributed securitysystem 100, various techniques can be used for monitoring which isdescribed on a sliding scale between always inline to never inline.First, in an always inline manner, all user traffic is between inlineproxies such as the processing nodes 110 or the cloud nodes 502 withoutexception. Here, DNS can be used as a forwarding mechanism to the inlineproxies. Second, in a somewhat always inline manner, all user trafficexcept for certain business partners or third parties is between inlineproxies such as the processing nodes 110 or the cloud nodes 502. Third,in an inline manner for most traffic, high bandwidth applications can beconfigured to bypass the inline proxies such as the processing nodes 110or the cloud nodes 502. Exemplary high bandwidth applications caninclude content streaming such as video (e.g., Netflix, Hulu, YouTube,etc.) or audio (e.g., Pandora, etc.). Fourth, in a mixed manner, inlinemonitoring can be used for “interesting” traffic as determined bysecurity policy with other traffic being direct. Fifth, in an almostnever inline manner, simple domain-level URL filtering can be used todetermine what is monitored inline. Finally, sixth, in a never inlinemanner, DNS augmented security can be used.

Referring to FIG. 6, in an exemplary embodiment, a network diagramillustrates a network 550 with a distributed security cloud 552providing DNS augmented security. The network 550 includes a user device554 connecting to the distributed security cloud 552 via an anycast DNSserver 556. The anycast DNS server 556 can be a server such as theserver 300 of FIG. 3. Also, the anycast DNS server 556 can be theprocessing node 110, the cloud node 502, etc. The distributed securitycloud 552 includes the anycast DNS server 556, policy data 558, and aninline proxy 560. The inline proxy 560 can include the processing node110, the cloud node 502, etc. In operation, the user device 554 isconfigured with a DNS entry of the anycast DNS server 556, and theanycast DNS server 556 can perform DNS surrogation as is describedherein. The distributed security cloud 552 utilizes the anycast DNSserver 556, the policy data 558, and the inline proxy 560 to perform theDNS augmented security.

The network 550 illustrates the DNS augmented security where DNSinformation is used as follows. First, at step 562, the user device 554requests a DNS lookup of a site, e.g. “what is the IP address ofsite.com?” from the anycast DNS server 556. The anycast DNS server 556accesses the policy data 558 to determine the policy associated with thesite at step 564. The anycast DNS server 556 returns the IP address ofthe site based on the appropriate policy at step 566. The policy data558 determines if the site either goes direct (step 568) to theInternet, is inspected by the inline proxy (step 570), or is blocked perpolicy (step 572). Here, the anycast DNS server 556 returns the IPaddress with additional information if the site is inspected or blocked.For example, if the anycast DNS server 556 determines the access isdirect, the anycast DNS server 556 simply returns the IP address of thesite. If the anycast DNS server 556 determines the site is blocked orinspected, the anycast DNS server 556 returns the IP address to theinline proxy 560 with additional information. The inline proxy 560 canblock the site or provide fully in line proxied traffic to the site(step 574) after performing monitoring for security.

The DNS augmented security advantageously is protocol and applicationagnostic providing visibility and control across virtually allInternet-bound traffic. For example, DNS-based protocols includeInternet Relay Chat (IRC), Session Initiation Protocol (SIP), HypertextTransfer Protocol (HTTP), HTTP Secure (HTTPS), Post Office Protocol v3(POP3), Internet Message Access Protocol (IMAP), etc. Further, emergingthreats are utilizing DNS today especially Botnets and advancedpersistent threats (APTs). For example, Fast flux is a DNS techniqueused to hide phishing and malware delivery sites behind an ever-changingnetwork of compromised hosts acting as proxies. The DNS augmentedsecurity provides deployment flexibility when full inline monitoring isnot feasible. For example, this can be utilized in highly distributedwith high bandwidth environments, in locations with challenging InternetAccess, etc. The DNS augmented security can provide URL filtering,white/black list enforcement, etc. for enhanced security without contentfiltering. In this manner, the network 550 can be used with thedistributed security system 100 and the cloud system 500 to providecloud-based security without requiring full inline connectivity.

§ 7.0 HSTS Security

Referring to FIGS. 7-14, in various exemplary embodiments, flow diagramsillustrate interactions between a user device 602, a browser/app 604 onthe user device 602, a server 606 associated with a requested domain, aneavesdropper 608, an HSTS application 610, and a cloud based proxygateway 612 for implementing the systems and methods. FIG. 7 illustratesthe interactions between the user device 602, the browser/app 604 on theuser device 602, and the server 606 associated with a requested domainillustrating cookie hijacking. FIG. 8 illustrates the interactionsbetween the user device 602, the browser/app 604 on the user device 602,and the server 606 associated with a requested domain illustratingUser-Agent exposure. FIG. 9 illustrates the interactions between theuser device 602, the browser/app 604 on the user device 602, and theserver 606 associated with a requested domain illustrating Authorizationexposure.

FIG. 10 illustrates the interactions between the user device 602, thebrowser/app 604 on the user device 602, the server 606 associated with arequested domain, the HSTS application 610, and the cloud based proxygateway 612 illustrating cookie security. FIG. 11 illustrates theinteractions between the user device 602, the browser/app 604 on theuser device 602, the server 606 associated with a requested domain, theHSTS application 610, and the cloud based proxy gateway 612 illustratingUser-Agent security. FIG. 12 illustrates the interactions between theuser device 602, the browser/app 604 on the user device 602, the server606 associated with a requested domain, the HSTS application 610, andthe cloud based proxy gateway 612 illustrating Authorization datasecurity. FIG. 13 illustrates the interactions between the user device602, the browser/app 604 on the user device 602, the server 606associated with a requested domain, the HSTS application 610, and thecloud based proxy gateway 612 illustrating optimized cloud based HSTS.FIG. 14 illustrates the interactions between the user device 602, thebrowser/app 604 on the user device 602, the server 606 associated with arequested domain, the HSTS application 610, and the cloud based proxygateway 612 illustrating cloud based HSTS for non-HSTS domains.

The user device 602 can be, for example, the computer device 220, themobile device 230, the server 300, the mobile device 400, any of thedevices in the locations 510, 520, 530, the mobile laptop 540, themobile device 542, or the user device 554. The browser/app 604 can beany application, program, browser, etc. executed on the user device 602and configured to communicate over a network using HyperText TransferProtocol (HTTP) or HTTPS. The server 606 can be similar to the server300 and is hosting a domain, such as domain.com as used in the variousexamples herein.

In FIGS. 7-9, as described herein, Internet users can simply typedomain.com such as in a browser address bar or the like in thebrowser/app 604 on the user device 602 to make a request to the server606 (step 620). The browser/app 604 makes an HTTP GET request todomain.com, i.e., the server 606 (step 622). In FIG. 7, the HTTP GETrequest can be GET/HTTP/1.x with COOKIE: <DATA>. In FIG. 8, the HTTP GETrequest can be GET/HTTP/1.x with USER-AGENT: <DATA: IE/8, WIN 6>. InFIG. 9, the HTTP GET request can be GET/HTTP/1.x with AUTHORIZATION:<DATA: CREDENTIALS>. As described herein, the COOKIE: <DATA>,USER-AGENT: <DATA: IE/8, WIN 6>, and the AUTHORIZATION: <DATA:CREDENTIALS> can be collectively referred to as sensitive information.FIGS. 7-9 illustrate three examples of sensitive information and thoseof ordinary skill in the art will recognize other types are alsocontemplated.

As described herein, the sensitive information is sent between thebrowser/app 604 to the server 606 as plain text, unencrypted. After step622, the server 606 sends a 307 redirect to instruct the browser/app 604to load an HTTPS version of domain.com (step 624). For example, this caninclude 307 TEMPORARY REDIRECT HTTP/1.x LOCATION: HTTPS://DOMAIN.COM.After the redirect, all communications between the browser/app 604 andthe server 606 are encrypted (step 626). Until the 307 redirect, allcommunication is in plain text, and the eavesdropper 608 can listen tothis information including the sensitive information for theft thereof.

The eavesdropper 608 is a malicious entity (the eavesdropper 608 isanother computing device) which listens to the GET request and acquiresthe sensitive information. Cookies are used by most of the onlineservices to authenticate and track user's personal details. User-Agentinformation has details about the browser/app 604 and operating system(OS) being used in the user device 602. This information can be used toattack the user device 602 using known issues with the browser/app 604or OS or zero-day attacks. A zero-day vulnerability refers to a hole inthe software that is unknown to the vendor. This security hole is thenexploited by hackers or the eavesdropper 608 before the vendor becomesaware and hurries to fix it. For Authorization, the WWW-Authenticatemechanism is still being used by many servers to authenticate users.Once this information is exposed, it is very easy to gain access touser's account.

Again, a browser-based HSTS approach solves the aforementioneddeficiencies in FIGS. 7-9 to some extent. Whenever the user typesdomain.com in a browser address bar in the browser/app 604, it isreplaced with the https instead making this communication over HTTPS instep 622. With browser-based HSTS, every domain.com is matched against apre-loaded list in the browser/app 604 to decide if it supports HTTPS.Again, not every variant of the browser/app 604 supports HSTS, thepreloaded list of HTTPS domains has a limited number of domains, it isnot possible to load billions of domains in the preloaded list, thepreloaded list is stored on the user device 602 taking storage space,and to update the list, intrusive updates are required in thebrowser/app 604. Further, the preloaded list is created by humans,introducing human error and correcting an erroneous list is cumbersome.

§ 7.1 Cloud Based HSTS

In various exemplary embodiments, the systems and methods utilize acloud based proxy to implement cloud based HSTS. Specifically, in FIGS.10-13, there is an HSTS app 610 on the user device 602 in addition tothe browser/app 604. The HSTS app 610 works to communicate with thegateway 612, securely, for the initial GET request. The gateway 612implements cloud based HSTS on the GET request, thereby removing therequirement for the user device 602 or the browser/app 604 to implementHSTS along with the aforementioned limitations including localmanagement of the preloaded list on the user device 602. The preloadedlist is managed in the cloud based proxy gateway 612, and its update isinstantaneous for all user devices 602 communicating through the gateway612.

In FIGS. 10-12, the user, through the browser/app 604, requests adomain, domain.com (step 650). The browser/app 604 initiates an HTTP GETrequest to the server 606 (step 652). Again, as described in FIGS. 7-9,the HTTP GET request here in step 652 includes the sensitiveinformation. In FIG. 10, the HTTP GET request can be GET/HTTP/1.x withCOOKIE: <DATA>. In FIG. 11, the HTTP GET request can be GET/HTTP/1.xwith USER-AGENT: <DATA: IE/8, WIN 6>. In FIG. 12, the HTTP GET requestcan be GET/HTTP/1.x with AUTHORIZATION: <DATA: CREDENTIALS>. Asdescribed herein, the COOKIE: <DATA>, USER-AGENT: <DATA: IE/8, WIN 6>,and the AUTHORIZATION: <DATA: CREDENTIALS> can be collectively referredto as sensitive information. FIGS. 10-13 illustrate three examples ofsensitive information and those of ordinary skill in the art willrecognize other types are also contemplated.

However, in FIGS. 10-12, with the cloud based proxy, the HSTS app 610intercepts the HTTP GET request and communicates with the gateway 612,ensuring the sensitive information is not sent as plain text. For everydomain, the HSTS app 610 makes a CONNECT request to the gateway 612(step 654). For example, CONNECT domain.com HTTP/1.x. The gateway 612responds to the HSTS app 610 with a proxy HSTS header along with otherheaders (step 656). For example, 200 OK HTTP/1.x PROXY-HSTS: ALLOW=1.Here, the gateway 612 determines the domain is allowed, and the headerinformation includes information about the domain (the server 606) suchas whether it supports HTTPS.

In FIGS. 10-12, it is assumed the domain (domain.com) through the server606 supports HTTPS, and such information is communicated in step 656. Ifthe domain.com supports HTTPS, the HSTS app 610 will remove allsensitive information from the first HTTP GET request in step 652 (step658). The gateway 612 will forward the first HTTP GET request from theHSTS app 610 with the sensitive information removed to the server 606(step 660). The server 606 responds with a 307 redirect to the gateway612, such as 307 TEMPORARY REDIRECT HTTP/1.x LOCATION:HTTPS://DOMAIN.COM (step 662). The gateway 612 sends the 307 redirect tothe HSTS app 610 (step 664), and the HSTS app 610 sends the 307 directto the browser/app 604 (step 666). Subsequent to the browser/app 604receiving the 307 redirect, all communication between the browser/app604 and the server 606 is encrypted (step 668).

Thus, the cloud based proxy, through the gateway 612, can maintain thepreloaded list and determine whether or not the domain, at the server606, supports HTTPS. Management of the preloaded list is simplified asit occurs at a single location, in the cloud based proxy. The HSTS app610 can perform the steps described herein for any domain request fromany browser/app 604 associated with the user device 602.

§ 7.2 Optimizing Cloud Based HSTS

In FIG. 13, the CONNECT request frequency is reduced, thereby optimizingthe cloud based HSTS. It is highly likely that if a domain supportsHTTPS, then all sub-domains will support HTTPS. If a sub-domain does notsupport HTTPS, it can be added to an exception list associated with thepreloaded list. In FIG. 13, the Proxy-HSTS header exchanged in step 656can be extended to include sub-domain support for HTTPS, therebyoptimizing the processes in FIGS. 10-12. For example, the step 656 canbe 200 OK HTTP/1.x PROXY-HSTS: ALLOW=1; EXCEPTION=SUB1 which includes anexample exception for SUB1 associated with the domain domain.com. TheHSTS app 610 will not send CONNECT requests for sub-domains. Also, theHSTS app 610 can generate local 307 redirect once it sees an HSTS domainfrom the gateway 612 (step 670). This eliminates the need for the HTTPGET request to the server 606 in FIGS. 10-12. Subsequent to thebrowser/app 604 receiving the 307 redirect, all communication betweenthe browser/app 604 and the server 606 is encrypted (step 672).Advantageously, this optimization in FIG. 13 where the HSTS app 610generates the 307 redirect locally on the user device 602 based on thegateway 612 reduces network utilization and terminates all insecureconnections on the user device 602 itself.

§ 7.2 Securing Non-HSTS Domains with the Cloud Based HSTS

In FIG. 14, non-HSTS domains (domains that do not support HTTPS) can besupported securely with the cloud based proxy supporting encryptedcommunication between the HSTS app 610 and the gateway 612. Here, thebrowser/app 604 initiates an HTTP GET request to the server 606 (step680). Again, the HTTP GET request includes the sensitive information,and it is received by the HSTS app 610 (step 682). For every domain, theHSTS app 610 makes a CONNECT request to the gateway 612 (step 684). Forexample, CONNECT domain.com HTTP/1.x. The gateway 612 responds to theHSTS app 610 with a proxy HSTS header along with other headers (step686). For example, 200 OK HTTP/1.x PROXY-HSTS: ALLOW=0. Here, thegateway 612 determines the domain is not allowed (it does not supportHSTS) and the header information includes information about the domain(the server 606) such as whether it supports HTTPS.

Once the HSTS app 610 finds the domain does not support HTTPS fromProxy-HSTS header in step 686, the HSTS app 610 will send that domain'srequest over an encrypted channel to the gateway 612 (step 688). Thisprotects against the eavesdropper 608 listening to the CONNECT requestwith plain text for the sensitive information. The gateway 612 canforward the HTTP GET request with the sensitive information to thedomain, the server 606 (step 690). The server 606 can respond with a 200OK HTTP/1.x <DATA> to the gateway 612 (step 692). The gateway 612 cansend the response from the server 606 to the HSTS app 610 via anencrypted channel (step 694). The HSTS app 610 can provide the response,e.g., 200 OK HTTP/1.x <DATA> to the browser/app 604 (step 696).

Thus, non-HSTS domains can be secured from the eavesdropper 608monitoring the user device 604. Here, the plain text communications ofthe sensitive information are between the gateway 612 and the server606. This is advantageous over other approaches such as IPSec-likeprotocol.

§ 7.3 Cloud Based HSTS Benefits

Again, the cloud based HSTS provides HSTS for all browsers and apps,regardless of their underlying support. It is easy to add new domainssupporting HSTS, by updating the preloaded list in the cloud basedproxy. No updates are needed to the browser/app 604 to update HSTSsupporting domain list, the preloaded list. Billions of domains can beadded to a cloud in the preloaded list. There is no local storage ofHSTS supporting domains on the user device 602. The cloud based proxycan auto-populate HSTS supporting domain list, the preloaded list,eliminating human involvement and associated efforts. Once an HSTSdomain is added to the list, it takes effect instantly in the cloudbased proxy. With optimization, the latency is reduced to zero ornegative by generating a local 307 redirect. Double encryption isavoided for domains already supporting HTTPS, such double encryptionwith other techniques. There are improvements in battery life at theuser device 602 by reducing overall encryption processing needed. Thus,the cloud based HSTS solves the deficiencies described herein withconventional HSTS approaches. The cloud based HSTS is less cumbersomeand no overhead of updates. Finally, the cloud based HSTS guaranteessecure and accurate implementation of HSTS.

It will be appreciated that some exemplary embodiments described hereinmay include one or more generic or specialized processors (“one or moreprocessors”) such as microprocessors; Central Processing Units (CPUs);Digital Signal Processors (DSPs): customized processors such as NetworkProcessors (NPs) or Network Processing Units (NPUs), Graphics ProcessingUnits (GPUs), or the like; Field Programmable Gate Arrays (FPGAs); andthe like along with unique stored program instructions (including bothsoftware and firmware) for control thereof to implement, in conjunctionwith certain non-processor circuits, some, most, or all of the functionsof the methods and/or systems described herein. Alternatively, some orall functions may be implemented by a state machine that has no storedprogram instructions, or in one or more Application Specific IntegratedCircuits (ASICs), in which each function or some combinations of certainof the functions are implemented as custom logic or circuitry. Ofcourse, a combination of the aforementioned approaches may be used. Forsome of the exemplary embodiments described herein, a correspondingdevice such as hardware, software, firmware, and a combination thereofcan be referred to as “circuitry configured or adapted to,” “logicconfigured or adapted to,” etc. perform a set of operations, steps,methods, processes, algorithms, functions, techniques, etc. as describedherein for the various exemplary embodiments.

Moreover, some exemplary embodiments may include a non-transitorycomputer-readable storage medium having computer readable code storedthereon for programming a computer, server, appliance, device,processor, circuit, etc. each of which may include a processor toperform functions as described and claimed herein. Examples of suchcomputer-readable storage mediums include, but are not limited to, ahard disk, an optical storage device, a magnetic storage device, a ROM(Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM(Erasable Programmable Read Only Memory), an EEPROM (ElectricallyErasable Programmable Read Only Memory), Flash memory, and the like.When stored in the non-transitory computer readable medium, software caninclude instructions executable by a processor or device (e.g., any typeof programmable circuitry or logic) that, in response to such execution,cause a processor or the device to perform a set of operations, steps,methods, processes, algorithms, functions, techniques, etc. as describedherein for the various exemplary embodiments.

Although the present disclosure has been illustrated and describedherein with reference to preferred embodiments and specific examplesthereof, it will be readily apparent to those of ordinary skill in theart that other embodiments and examples may perform similar functionsand/or achieve like results. All such equivalent embodiments andexamples are within the spirit and scope of the present disclosure, arecontemplated thereby, and are intended to be covered by the followingclaims.

What is claimed is:
 1. A method for HyperText Transfer Protocol (HTTP)HTTP Strict Transport Security (HSTS), implemented by one or moreservers associated with a gateway in a cloud based proxy, the methodcomprising: managing a preloaded list of HTTP Security (HTTPS) supportof a plurality of domains; receiving a domain request from an HSTSapplication executed on a user device, wherein the HSTS application isconfigured to detect the domain request from a browser or applicationexecuted on the user device; and transmitting a response to the userdevice with header information related to support of HTTPS the domain.2. The method of claim 1, further comprising: subsequent to thereceiving and prior to the transmitting, determining the support ofHTTPS of the domain.
 3. The method of claim 2, wherein the determiningcomprises: sending a request to the domain without sensitive informationfrom the domain request; and receiving a redirect from the domain. 4.The method of claim 2, wherein the determining comprises checking thepreloaded list and wherein the header information comprises anyexceptions based on the preloaded list.
 5. The method of claim 1,wherein the HSTS application removes sensitive information from thedomain request prior to the receiving.
 6. The method of claim 1, whereincommunications between the user device and the gateway are secure. 7.The method of claim 6, wherein the domain does not support HSTS, andfurther comprising: transmitting the domain request with sensitiveinformation in plain text between the gateway and the domain.
 8. Agateway in a cloud based proxy, configured to implement HyperTextTransfer Protocol (HTTP) HTTP Strict Transport Security (HSTS), thegateway comprising: a network interface, a data store, and a processorcommunicatively coupled to one another; and memory storing computerexecutable instructions, and in response to execution by the processor,the computer-executable instructions cause the processor to performsteps of managing a preloaded list of HTTP Security (HTTPS) support of aplurality of domains; receiving a domain request from an HSTSapplication executed on a user device, wherein the HSTS application isconfigured to detect the domain request from a browser or applicationexecuted on the user device; and transmitting a response to the userdevice with header information related to support of HTTPS the domain.9. The gateway of claim 8, wherein the memory storing computerexecutable instructions, and in response to execution by the processor,the computer-executable instructions further cause the processor toperform steps of subsequent to the receiving and prior to thetransmitting, determining the support of HTTPS of the domain.
 10. Thegateway of claim 9, wherein the determining comprises: sending a requestto the domain without sensitive information from the domain request; andreceiving a redirect from the domain.
 11. The gateway of claim 9,wherein the determining comprises checking the preloaded list andwherein the header information comprises any exceptions based on thepreloaded list.
 12. The gateway of claim 8, wherein the HSTS applicationremoves sensitive information from the domain request prior to thereceiving.
 13. The gateway of claim 8, wherein communications betweenthe user device and the gateway are secure.
 14. The gateway of claim 13,wherein the domain does not support HSTS, and wherein the memory storingcomputer executable instructions, and in response to execution by theprocessor, the computer-executable instructions further cause theprocessor to perform steps of transmitting the domain request withsensitive information in plain text between the gateway and the domain.15. A method for HyperText Transfer Protocol (HTTP) HTTP StrictTransport Security (HSTS), implemented by a user device in communicationwith a gateway in a cloud based proxy, the method comprising: detectinga domain request from a browser or application executed on the userdevice by an HSTS application on the user device; securely forwardingthe domain request to a gateway; receiving a response from the gatewaywith header information related to HTTP Security (HTTPS) support of thedomain; and responsive to the domain supporting HTTPS based on theheader information, securely communicating with the domain.
 16. Themethod of claim 15, wherein the browser or application does not supportHSTS.
 17. The method of claim 15, wherein the HSTS application removessensitive information from the domain request prior to the forwarding.18. The method of claim 15, wherein the gateway determines whether thedomain supports HTTPS independent of the user device.
 19. The method ofclaim 18, wherein the gateway determines through a request sent to thedomain without sensitive information from the domain request; andreception of a redirect from the domain.
 20. The method of claim 18,wherein the gateway determines by checking a preloaded list managedthereon of HTTPS supporting domains and wherein the header informationcomprises any exceptions based on the preloaded list.